home *** CD-ROM | disk | FTP | other *** search
- Path: news.iadfw.net!usenet
- From: Larry Weiss <lfw@iadfw.net>
- Newsgroups: comp.std.c
- Subject: externsions and Standard C
- Date: Sat, 23 Mar 1996 09:30:02 -0600
- Organization: customer of Internet America
- Message-ID: <315418FA.1508@iadfw.net>
- References: <4gum82$14v4@info4.rus.uni-stuttgart.de><MIB.96Mar15170902@gnu.ai.mit.edu><wyraut5fqq.fsf@dns.bluesky.net><MIB.96Mar16174948@gnu.ai.mit.edu><4ifq40$i87@sundog.tiac.net><MIB.96Mar18105957@gnu.ai.mit.edu><danpop.827188302@rscernix> <MPLANET.31530e9djcoffin98993e@news.rmii.com> <31536199.219868914@nntp.ix.netcom.com>
- NNTP-Posting-Host: dal10-21.ppp.iadfw.net
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.01 (Win16; I)
-
- Mike Rubenstein wrote:
- >
- > You've missed a rather subtle point. Such extensions are legal but
- > they do not introduce integer types. The standard defines the signed
- > integer types as being signed char, short int, int, and long int (and
- > similarly for unsigned integer types). An implementation may
- > introduce new types that behave like integers, but according to the
- > standard they are not integer types.
- >
- > This is important since it guarantees, for example, that size_t is
- > unsigned char, unsigned short, unsigned int, or unsigned long. An
- > implementation cannot define size_t as being unsigned _VeryLong
- > (assuming, of course, that unsigned _VeryLong is a new type).
- >
-
- It must be pretty subtle! Can you cite specific Clause references to help me
- sort out this distinction?
-